-
-
Notifications
You must be signed in to change notification settings - Fork 0
feat: add module for a kotlin plugin #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
| publishing.repositories(repos -> repos.maven(maven -> { | ||
| String version = p.getVersion().toString(); | ||
| String baseUrl = version.contains("SNAPSHOT") | ||
| ? "https://repo.onelitefeather.dev/onelitefeather-snapshots" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be a property for gradle or system property
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This would be a separate pull request and isn’t really related to this one
| applyCommonPlugins(project); | ||
| configureTesting(project); | ||
| configurePublishing(project); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add conditions here ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How would you design such conditions? Just using properties? I’m not very experienced in writing plugins, so I can’t suggest the best solution
Proposed changes
The pull request adds a module which contains a kotlin plugin which does the same as the given java plugin.
Types of changes
What types of changes does your code introduce to this project?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any ofthem, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.